Package | hl7.fhir.uv.cmhaffr2 |
Type | Requirements |
Id | Id |
FHIR Version | R5 |
Source | http://hl7.org/fhir/uv/cmhaffr2/https://build.fhir.org/ig/HL7/cmhaff-ig/Requirements-CMHAFFR2-PDS.html |
Url | http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-PDS |
Version | 2.0.1 |
Status | active |
Date | 2025-01-30T10:38:20+00:00 |
Name | Product_Development___Support |
Title | Product Development & Support |
Experimental | False |
Realm | uv |
Authority | hl7 |
Description | Prior to marketing a mobile app, the developer has a responsibility to ensure it meets Realm-specific rules and regulations. Although cMHAFF does not have guidelines for all aspects of the software product life cycle, cMHAFF still recommends that the product development life cycle, for new apps and for upgrades to apps, ensure that requirements for functionality, reliability, performance, scalability, safety, compatibility, portability, and maintainability have been addressed, as well as any requirements that relate to aspects that include these items previously described above: * Product Information for consumers (e.g., App Store descriptions, product disclosures) * Security * Privacy * Permission to use device features * Data Access * Data Sharing * Terms of Use, Conditions * Product Development, including risk management, user-centered design, compliance with applicable regulations, functions (product description), reliability, performance, scalability, safety, compatibility, and portability. The security and privacy of information used by the app needs to be considered throughout the development phases of the app. Functionality must support the intended use of the app for the target users and stakeholders. Thorough and iterative risk assessment and requirement analysis, testing, evidence collection, documentation, and configuration management ensures quality to satisfy the needs of the application’s various stakeholders 8 . Assessing the usability of the app helps ensure the app’s viability and adoption; testing must be population- relevant and demonstrate reasonable product usability (accessibility) by people with visual, auditory and motor disabilities within the intended target audience. Establishing a system of customer support enables product defects and usability issues to be surfaced in a systematic way and helps problems related to use of the app to be effectively resolved and the developer to continually deliver the intended use of the app. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
{
"resourceType" : "Requirements",
"id" : "CMHAFFR2-PDS",
"meta" : {
"profile" : [
"http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMSection"
]
},
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: Requirements CMHAFFR2-PDS</b></p><a name=\"CMHAFFR2-PDS\"> </a><a name=\"hcCMHAFFR2-PDS\"> </a><a name=\"CMHAFFR2-PDS-en-US\"> </a><table class=\"grid\"/></div>"
},
"url" : "http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-PDS",
"version" : "2.0.1",
"name" : "Product_Development___Support",
"title" : "Product Development & Support",
"status" : "active",
"date" : "2025-01-30T10:38:20+00:00",
"publisher" : "HL7 International / Mobile Health",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/mobile"
}
]
}
],
"description" : "Prior to marketing a mobile app, the developer has a responsibility to ensure it meets Realm-specific rules and regulations.\nAlthough cMHAFF does not have guidelines for all aspects of the software product life cycle, cMHAFF still recommends\nthat the product development life cycle, for new apps and for upgrades to apps, ensure that requirements for functionality,\nreliability, performance, scalability, safety, compatibility, portability, and maintainability have been addressed, as well as any\nrequirements that relate to aspects that include these items previously described above:\n* Product Information for consumers (e.g., App Store descriptions, product disclosures)\n* Security\n* Privacy\n* Permission to use device features\n* Data Access\n* Data Sharing\n* Terms of Use, Conditions\n* Product Development, including risk management, user-centered design, compliance with applicable regulations,\nfunctions (product description), reliability, performance, scalability, safety, compatibility, and portability.\nThe security and privacy of information used by the app needs to be considered throughout the development\nphases of the app. Functionality must support the intended use of the app for the target users and stakeholders.\nThorough and iterative risk assessment and requirement analysis, testing, evidence collection, documentation, and\nconfiguration management ensures quality to satisfy the needs of the applicationâs various stakeholders 8 .\nAssessing the usability of the app helps ensure the appâs viability and adoption; testing must be population-\nrelevant and demonstrate reasonable product usability (accessibility) by people with visual, auditory and motor\ndisabilities within the intended target audience. Establishing a system of customer support enables product\ndefects and usability issues to be surfaced in a systematic way and helps problems related to use of the app to be\neffectively resolved and the developer to continually deliver the intended use of the app.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.